Load the iOS Standard Client

Remember, for Apple devices, the standard Digitise Apps Client is made available to be used by developers during the development of your Digitise apps. It MUST NOT be used on your end-users' devices, even for testing.

 

To load the Client on a developer's test iOS device, tap on the Digitise Apps icon, Picture showing the Standard Digitise Apps Client icon as displayed in the device's Apps list., on the Home screen.

 

The first time you load the Client, you may see a message telling you that your organisation has not been trusted on the device. If you get this message you will need to add your organisation as a trusted developer - see Configure the Digitise Apps Client on a Developer's Test Apple Device for information about how to do this.

You may also get a message informing you that the Client would like to send you notifications. You should tap OK, to ensure you receive these notifications. Users can subsequently configure and enable/disable notifications on a per-app basis within the device's Settings.

 

If the Client has been configured to require the user to log in using Digitise Apps credentials or Windows Active Directory Authentication a Login screen will be displayed and you will need to log in. For example, on an iPad the login takes the form of a popup over the Home screen:

Picture showing the login fields in the standard Digitise Apps Client on an iPad.

 

If your Client has been configured to login using Google OAuth rather than using Digitise Apps credentials or Windows Active Directory Authentication, the Client will attempt to connect to Google to authenticate the user instead and, if successful, the Google login screens will be displayed.

 

If the login fields shown above appear, you will need to log in or cancel. The user login determines which Digitise apps will be available to the user. If you only want to view or edit the Client configuration and don't intend to download or use any apps, you can cancel the login, which should still allow you to access the configuration settings.

If you want to log in, you will need to obtain the login credentials from your Digitise Apps Administrator, if you don't already have them.

To log in anonymously, simply select the Anonymous option.

If you are given just a username and password, enter these in the appropriate boxes on the screen. If there is a value in the Domain field, you will need to delete this. Note that if you are unable to delete this field, this means that the Client has been configured to only allow Windows authentication and you cannot log in as a Digitise Apps User. If the Domain field is missing, this means that the developers have removed it because it isn't required for you to login.

To log in using Windows authentication you will need a domain, username and password. You can enter the domain name in the Domain field or include it with your username in the Username field in the standard format:

<domainname>\<username>

Including the domain name in the Username field will overwrite any domain name specified in the Domain field. If you cannot delete an existing value from the Domain field, you cannot include the domain in the Username field and attempting to do so will display an error message.

By default, values you enter in the Username field and, if shown, the Domain field are automatically saved and filled in the next time the Login screen is displayed. When building a pre-configured version of the Digitise Apps Client, you can turn off username saving within the build request options, if required.

If the Save Password option is displayed, you can instruct the Client to remember your password as well and automatically fill in the password field the next time you log in. To save your password, select the Save Password option. The password entered will be stored in an encrypted database on the device. If the option is missing, the Client has had the Save Password option pre-set and locked to prevent users from saving their passwords and you cannot change the setting within the Client.

The saved values are only used to fill in the Login fields, the user will still have to tap Picture showing the Done button in the standard Digitise Apps Client on an iOS device. to log in.

 

If you log in anonymously after logging in as a Digitise Apps User or Domain User, the next time the login displays, the Username and Password fields will be blank but a previously entered domain will be displayed again.

 

When you have entered your credentials, tap Picture showing the Done button in the standard Digitise Apps Client on an iOS device..

 

If this is the first time you have run the Client, the Client's Home Screen will look like this:

Picture showing the Digitise Apps Client Home Screen on an iOS device.

If the Digitise Apps Client hasn't been pre-configured with the App Server address you will need to enter the address before you can download any Digitise apps.

When you have entered the App Server address, you can tap the Refresh button, Picture showing the Refresh button in the standard Digitise Apps Client on an iOS device., in the bottom left-hand corner of the Home screen to check for new apps or updates. Note that if you have restricted access within App Manager to any of your apps only those which have been assigned to the current user/device will be available to download.

 

If you have already downloaded apps to this device, when you load the Client the Home screen will list any apps you have already downloaded and any which are still available to download:

Picture showing the Home screen of the standard Digitise Apps Client on an iPad, showing Apps available for download and Apps already downloaded.

If the Client is configured to check for updates on startup, when you load the Client, it will automatically check for updates or new apps with the App Server. This option can be configured when building your Client and can be set to read-only in which case it cannot be changed within the Client. If the option hasn't been pre-configured or hasn't been set to read-only, you can enable or disable the option within the Client's Settings.